Ad Lib Multimedia inc.
580, Grande-Allee Est, suite 40
Quebec, QC. Zip Code : G1R 2K2
Telephone : (418) 522-6100

                         ADLIB Multimedia, Quebec

For the installing informations, please read the INSTALL.TXT file.

READ.ME - OS/2 Ad Lib Audio Device Driver Installation Version 1.5
-------------------------------------------------------------------------------
This file contains detailled informations on how to install
the Ad Lib multimedia Audio Device drivers for the Ad Lib's sound cards.

In addition to Ad Lib Audio driver installation, this diskette allows for
the optional installation of IBM's MPU-401 and OPL3 MIDI drivers.

The following topics are covered in this READ.ME file :
1)  Installing on top of previous installations
2)  System Requirements
3)  Files List for Ad Lib Audio Install Disk
4)  Ad Lib Audio for OS/2 Installation Procedure
5)  Device Driver Command Line Options
6)  Notes on Command Line Options
7)  Using Audio in DOS and Win-OS/2 Sessions
8)  Audio Concurrency Issues - OS/2, DOS, Win-OS/2
9)  Plug and Play System Issues
10) Mixer Issues
11) MIDI Issues
12) OPL3 Device Driver
13) MPU401 Device Driver


1)  Installing on top of previous installations
-------------------------------------------------------------------------------
Prior to installing, check if the following lines exists in CONFIG.SYS:
    BASEDEV=CS31CONF.SYS ...
    BASEDEV=CS32CONF.SYS ...
    DEVICE=C:\MMOS2\CSBSAUD.SYS ...
    DEVICE=C:\MMOS2\VCSBSAUD.SYS BSAUD1$
    DEVICE=C:\MMOS2\VCSGAMES.SYS BSAUD1$
If any of these entries are present, delete them prior to installing this
product.


2)  System Requirements
-------------------------------------------------------------------------------
Before you install Ad Lib Audio for OS/2, check to see if you have the
version of MMPM/2 as shipped with OS/2 2.11, or later, installed on your
system.  Use the SYSLEVEL command to determine which level of MMPM/2 you have
installed.  The "Current CSD Level" field displays one of the following
values:

    UN0000  - The version of MMPM/2 as shipped with OS/2 2.1. An update
               is required.
    UN49407 - The October 1993 CSD version of MMPM/2.
               An update is required.
               This is the same version for the OS/2 2.11 service
               refresh of February 1994.
    XR03000 - The version of MMPM/2 as shipped with OS/2 Warp 3.0.
               No update is required.

If an update is required, the MMPM/2 CSD can be obtained free from
Compuserve or from the IBM OS/2 BBS.

CompuServe: OS/2 Support Forum:
    Library 17: mmpmcs.dsk

IBM BBS: (919) 517-0001
    mmoscsd.dsk



3)  File List for Ad Lib Audio Install Disk
-------------------------------------------------------------------------------
Ad Lib Audio Files :
BSAUDRES.DLL    -   OS/2 business audio support DLL.
BUSAUDIO.HLP    -   Help file used during installation of Ad Lib Audio.
CARDINFO.DLL    -   Ad Lib device support DLL.
CONTROL.SCR     -   Installation control file, used by
                    the standard OS/2 multimedia instalation program.
CSBSAUD.INI     -   OS/2 defaults audio settings.
CSBSAUD.SYS     -   OS/2 audio physical device driver for Ad Lib Audio.
CS32CONF.SYS    -   OS/2 audio configuration device driver for CS4232.
CWAUDIO.BIN     -   OS/2 audio device microcode.
FILES.32        -   File list for CS4232 installation.
READ.ME         -   This file.
VCSBSAUD.SYS    -   OS/2 audio virtual device driver for Crystal Audio.
INSTALL.TXT     -   Step-by-step installation procedure.

IBM OPL3 Files :
OPL3.SYS        -   OS/2 audio physical device driver for IBM OPL3 FM MIDI.
OPL3.HLP        -   Help file used during installation of IBM OPL3 FM MIDI.
OPL3RES.DLL     -   IBM OPL3 device support DLL.
OPLREAD.ME      -   Documentation for IBM OPL3 FM MIDI installation.

IBM MPU401 Files :
MPU401.SYS      -   OS/2 audio physical device driver for IBM MPU401 MIDI.
MPURES.DLL      -   IBM MPU401 device support DLL.
MPUREAD.ME      -   Documentation for IBM MPU401 MIDI installation.

IBM Misc. Files :
MIDIPLAY.ICO	-   Desktop ICON for MIDI player.
CLOCK01.SYS     -   OS/2 ISA clock driver that supports the highres timer.
CLOCK02.SYS     -   OS/2 MCA clock driver that supports the highres timer.
TIMER0.SYS      -   OS/2 highres timer driver.


note : CS4232 is the Ad Lib audio adapter. It was designed and
       build by Crystal Semiconductor Corporation.

       OPL3 is an FM music synthetiser chip originaly designed by AdLib
       and physicaly build by Yamaha.

4)  Ad Lib Audio for OS/2 Installation Procedure
-------------------------------------------------------------------------------
To install device support, insert the Ad Lib Audio for OS/2 diskette in
drive A: (or whichever drive Ad Lib Audio for OS/2 diskette is in).
Start the Multimedia Application Install program which is located in the
Multimedia folder on the OS/2 desktop.  Once you are in the multimedia
installation program, select Source Drive A: (or whichever drive Ad Lib
Audio for OS/2 diskette is in).

The installation program show 3 choices. Select all of them if it's your
first installation. You can also run the Application Install many time to
install each set of drivers separately.

Read and follow the instructions provided by the installation program.
The following files will be moved onto your system :

If Ad Lib ASB audio adapter is installed :
   \MMOS2\DLL\CARDINFO.DLL
   \MMOS2\DLL\BSAUDRES.DLL
   \MMOS2\HELP\BUSAUDIO.HLP
   \OS2\CS32CONF.SYS
   \MMOS2\CSBSAUD.SYS
   \MMOS2\VCSBSAUD.SYS
   \MMOS2\CSBSAUD.INI
   \MMOS2\CWAUDIO.BIN

If IBM OPL3 is installed :
	\MMOS2\OPL3.SYS
	\MMOS2\HELP\OPL3.HLP
	\MMOS2\DLL\OPL3RES.DLL

If IBM MPU401 is installed :
	\MMOS2\MPU401.SYS
	\MMOS2\DLL\MPURES.DLL

If either OPL3 or MPU401 are installed :
	\MMOS2\INSTALL\MIDIPLAY.ICO
	\OS2\BOOT\CLOCK01.SYS
	\OS2\BOOT\CLOCK02.SYS
	\OS2\BOOT\TIMER0.SYS


Based on your responses to input panels, several lines will be added to the
OS/2 CONFIG.SYS file.  If you do not know how to respond to the input panels,
it is best to NOT change the default settings and click the OK button.  The
following describes the modifications made to your OS/2 CONFIG.SYS file if no
settings are modified, based on the device selected :

If Ad Lib audio adapter is installed :
    BASEDEV=CS32CONF.SYS /P:534 /I:5 /D:1,1 /SB:220 /M:330,9 /FM:388 /J:200 /CD:NONE /O
    DEVICE=C:\MMOS2\CSBSAUD.SYS /N:BSAUD1$ /L:8
    DEVICE=C:\MMOS2\VCSBSAUD.SYS BSAUD1$

If either OPL3 or MPU401 are installed :
	BASEDEV=TIMER0.SYS
	DEVICE=C:\MMOS2\OPL3.SYS /P:388 /N:OPL31$
	DEVICE=C:\MMOS2\MPU401.SYS /N:MPU4011$

note : if you need to change the I/O ports, DMA or IRQ number, you can
       start again the installation program or you can directly edit
       your config.sys file with your favorite text editor.


5)  Device Driver Command Line Options
-------------------------------------------------------------------------------
The following tables describe the various command line options and setting
available for the Ad Lib Audio device drivers.

CS32CONF.SYS    -   OS/2 audio configuration device driver for CS4232.

Option/Format       Description                 Valid Values (* = Default Value)
-------------------------------------------------------------------------------
/P:<port>           Codec Port                  *534, 608, E84, F44 (hex)
/I:<irq>            Codec IRQ                   *5, 7, 9, 3, 4, ^10 (decimal)
/D:<pDMA,cDMA>      Playback,Capture DMA        ^0, 1, 3 (*1,1)
/CS:<port>          Control Port                (not required)
/SB:<port>          Sound Blaster Port          *220, 240, NONE
/M:<port,irq>       MPU Port                    330, *NONE
                    MPU IRQ                     5, 7, *9, 3, 4, ^10, NONE
/FM:<port>          FM Port                     *388, NONE
/J:<port>           Joystick Port               100, 200, *NONE
/CD:<port>          CD-ROM Port                 320, 340, 360, *NONE
/DL:<option>        Download microcode          Force, No (*not required)
/O                  Override PnP settings       /o (standard)
/V                  Enable Verbose Display      (*not enabled)

^(NOT ASB 16 Special Edition)



CSBSAUD.SYS     -   OS/2 audio physical device driver.  This driver supports all
                    Ad Lib Audio devices.

Option/Format       Description                 Valid Values (* = Default Value)
-------------------------------------------------------------------------------
/N:<name>           Name of PDD                 Supplied by install program (*BSAUD1$)
/X1:<value>         AUX1 unmute/gain            0..31 (8 = 0dB)  (*not enabled - muted)
/X2:<value>         AUX2 unmute/gain            0..31 (8 = 0dB)  (*not enabled - muted)
/L:<value>          LINE unmute/gain            0..31 (8 = 0dB)  (*not enabled - muted)
/R:<rate>           Enable Adj Intrpt Rate      1..60 (interrupts/sec) (*not enabled)
/EXT                Preserve Mixer Input        (*not enabled)
/M:<option>         Microphone Monitoring       1, On (*not enabled)
/S:<value>          Inactivity power down       1..5 minutes (*not enabled)
/V                  Enable Verbose Display      (*not enabled)





VCSBSAUD.SYS     -  OS/2 audio virtual device driver.  This driver supports all
                    Ad Lib Audio devices.

Option/Format       Description                 Valid Values (* = Default Value)
-------------------------------------------------------------------------------
                    Name of PDD                 Supplied by install program (*BSAUD1$)
/S                  Skip DOS Envir Var Scan     (*not enabled)





6)  Notes on Command Line Options
-------------------------------------------------------------------------------
 CSBSAUD.INI vs Command line options:
 There are two ways to supply CSBSAUD.SYS with options that override default
 settings. The first method is by supplying command-line options in the
 CONFIG.SYS file as specified above. The second method is by supplying entries
 in the CSBSAUD.INI file in the \MMOS2 directory. The first method overrides
 the second on an individual entry basis. Therefore, entries in CSBSAUD.INI
 will be used only when that particular option is not specified in CONFIG.SYS.

 VCSBSAUD.SYS /S Option:
 The VCSBSAUD.SYS driver will automatically set a 'BLASTER' DOS environment
 variable to the proper audio hardware settings.  This is done by adding a
 '@SET BLASTER=' line to the beginning of all DOS session's autoexec file.
 This file is specified in DOS session's DOS_AUTOEXEC property.  The /S option
 for VCSBSAUD.SYS will skip the automatic setting of this environment variable.

 CSBSAUD.SYS /R Option:
 The CSBSAUD.SYS /R option will allow the user to adjust the device interrupt
 rate.  This option should be used with caution.




7)  Using Audio in DOS and Win-OS/2 Sessions
-------------------------------------------------------------------------------
To enable Audio for DOS and Win-OS/2 sessions, you must set DOS properties
to the following:

    WIN_RUN_MODE                 3.1 ENHANCED COMPATIBILITY
    AUDIO_ADAPTER_SHARING        Required or Optional
    INT_DURING_IO                On
    HW_TIMER                     On
    VIDEO_SWITCH_NOTIFICATION    On
    VIDEO_8514A_XGA_IOTRAP       Off
    VIDEO_RETRACE_EMULATION      Off
    DPMI_MEMORY_LIMIT            8




8)  Audio Concurrency Issues - OS/2, DOS, Win-OS/2
-------------------------------------------------------------------------------
OS/2 MMPM/2 is designed such that, when an application is running in
the foreground (has focus), then that application takes priority over
others running in the background.  Background applications are put on hold
until they are placed in the foreground (have focus).

When you have a single audio device, it is not possible for two programs
to use the device at the same time.  For example, if one application has
the device configured for audio playback, and a second application also
configures the device for audio playback, the application with the focus
takes priority and the application in the background is placed on hold.
This situation also exists for sampling rate and sample size configuration.

Audio device drivers for Windows, installed under Win-OS/2, attempt to use
the audio device in all Windows sessions.  For Win-OS/2 sessions which do
not use the audio device, you can set the AUDIO_ADAPTER_SHARING property
to "None".  This prevents the session from accessing the audio device, and
enables the device to be used by other applications.

To display OS/2 online documentation pertinent to system audio, use
view.exe.  Suggested viewing items are:

    VIEW /AUDIO
    VIEW /MULTIMEDIA
    VIEW /SOUNDS



9)  Plug and Play System Issues
-------------------------------------------------------------------------------
The ASB 16 is a Plug and Play (PnP) compatible device.  If the system contains
a PnP BIOS, the command line options are ignored unless resource data is
not available or /O override option is specified.



10) Mixer Issues
-------------------------------------------------------------------------------
As of this release, there is no generic OS/2 mixer application for Business
Audio.  Therefore, the volume control for devices attached to mixer LINE, AUX1,
and AUX2 is established on the command line of the CSBSAUD.SYS driver.  Refer to
section 5, CSBSAUD.SYS, for the format of the unmute and gain setting options.

These values for gain are set on each boot and cannot be altered during system
operation.  The command line values represent a gain setting where 8 is equal
to 0 dB gain.  Each increment is 1.5 dB.  Values greater than 8 will reduce the
volume and values less than 8 increase the volume.

The devices attached to LINE, AUX1, and AUX2 are system dependent and cannot be
detailed here.  Refer to your system documentation for device configuration.

Note: These settings do not effect standard wave audio volume which is controlled
by the OS/2 volume control ICON.


11) MIDI Issues
-------------------------------------------------------------------------------
This installation diskette allows for the optional installation of the IBM OPL3
and MPU401 MIDI drivers. These drivers are provided to the user as a convenience.
The Ad Lib sound card support MIDI audio both by OPL3 and by MIDI command.

If you have the Ad Lib sound card called "special edition" (no wave table),
you will hear nothing when using the "MIDI 2" icon.

If you have an Ad Lib sound card with wave table, you will hear a more
realistic music. Unfortunately, unless you a have a third part mixer that
send standard MIDI command for the volume control, you will not be able
adjust the volume.


12) OPL3 Device Driver
-------------------------------------------------------------------------------
FM Synthesis OPL3 Midi Device Driver Installation
-----------------------------------------------------------

System Requirement
------------------
Before you install FM Synthesis OPL3 Midi, make sure that
you have installed OS/2 WARP Version 3.00 Revision 8.162.
Enter "VER /R" from an OS/2 command prompt to verify.


FM Synthesis OPL3 Midi for OS/2 Installation Procedure
-------------------------------------------------------------
To install device support, insert the FM Synthesis OPL3 Midi
for OS/2 diskette in drive A:. Start the multimedia installation
program "A:MINSTALL", located on the diskette.
Select the FM Synthesis OPL3 Midi" icon.

The Multimedia installation program adds the following statements
to your CONFIG.SYS file.  These statements are
displayed as follows:

   DEVICE=c:\mmos2\TIMER0.SYS
   DEVICE=c:\mmos2\opl3.sys /P:330 /N:OPL31$


13) MPU401 Device Driver
-------------------------------------------------------------------------------
OS/2* DEVICE DRIVER FOR MMPM/2 MPU-401 SUPPORT

  PLEASE READ THE FOLLOWING TERMS AND CONDITIONS.  YOUR
  USE OF THE OS/2 DEVICE DRIVER FOR MMPM/2 MPU-401 SUPPORT
  INDICATES YOUR ACCEPTANCE OF THE FOLLOWING
  TERMS AND CONDITIONS:

  o   YOU MUST BE A LICENSEE OF OS/2.
  o   YOU MAY MAKE COPIES OF THE OS/2 DEVICE DRIVER FOR
      MMPM/2 MPU-401 SUPPORT EQUAL TO THE
      NUMBER OF LICENSED COPIES OF OS/2 YOU POSSESS.
  o   ALL OTHER TERMS AND CONDITIONS OF YOUR OS/2
      LICENSE AGREEMENT APPLY TO THIS OS/2 DEVICE
      DRIVER FOR MMPM/2 MPU-401 SUPPORT;
      HOWEVER, THIS DOES NOT EXTEND ANY WARRANTY
      OUTLINED IN SUCH AGREEMENT.


  CONTENTS
  ________


           1.0  Supported Features

           2.0  Compatibility

           3.0  Preliminary Steps

           4.0  Installation from Diskette

           5.0  Optional Command-line Parameters

           6.0  Bugs

           7.0  Trademarks


 1.0  SUPPORTED FEATURES
  __________________

      This file describes the installation of the MMPM/2 MPU-401 device
      driver, MPU401.SYS, and related files.  This driver uses the new
      highres timer driver, TIMER0.SYS.

      The MPU-401 driver is actually a dual-function driver, as it supports
      both MMPM/2 and the new real-time MIDI subsystem.  Therefore, some of
      the command-line parameters may have limited or no functionality when
      taken in the context of MMPM/2 only.

   The MMPM/2 MPU-401 driver has the following functions:


     1. Uses the highres timer driver to provide 1-millisecond accuracy, the
        highest of any MMPM/2 MIDI driver.  A command-line parameter allows
        selecting a lower frequency if necessary.

     2. Supports up to 8 events independent events, including the new
        recurring events.

     3. Performs autodetection of MPU-401 hardware.  Can support up to 9
        MPU-401's (although MMPM/2 only recognizes 1)

     4. Automatically uses the 32ms system timer if the highres timer driver
        is not found.  Timing is reasonably accurate at 32ms.


 2.0 COMPATIBILITY
  _____________

  This graphics accelerator driver is compatible with
  OS/2 Warp 3.

 3.0  PRELIMINARY STEPS
  _________________

  If there are any copies of CLOCK01.SYS and CLOCK02.SYS in the
  x:\os2 (where x is the boot drive) directory, delete them.

  Be sure that CLOCK01.SYS and CLOCK02.SYS are not marked as READONLY.
  To remove the READONLY attributes, use the attrib command such as
  attrib -r x:\os2\boot\clock0*.sys, where x is the boot drive.


 4.0 INSTALLATION
  _________________

  Unzip the files (or insert the disk), run MINSTALL, and change the directory
  to point to where the files are located.

  MINSTALL will ask how many MPU-401's are installed.  Always answer with 1.

  5.0 Optional Command-line Parameters
  _________________

  The driver attempts to detect the base I/O ports and IRQ's during boot
  time.  The first valid port that it finds is the one that it uses.  In
  most cases, command-line parameters will not be required.  The driver
  currently only supports one MPU-401 when used with MMPM/2.

  Autodetect first looks at address 0x330 and then 0x300.  If used on a
  Microchannel machine, 0x1330 is also checked.

  Alternatively, command-line parameters can be used to tell the driver to
  skip the autodetect and use given I/O ports and IRQ's instead.  Up to
  9 MPU-401's, numbered 1 to 9, can be supported this way.  MPU-401 #1
  is the one that MMPM/2 uses.

  Parameters are in the format of:

       DEVICE=MPU401.SYS /xn:yyy /xn:yyy ...

        Where 'x' is a single capital letter, 'n' is from 1 to 9, and 'yyy' is
        the option.

        /Pn:yyy  Base I/O: Sets the base I/O address for port n, usually 300
                 or 330 (# is in hex)

        /In:yyy  IRQ level: Sets the IRQ level for port n.  yyy is a decimal
                 number from 1 to 15.  If the base I/O address for a given
                 port is specified (e.g. /P1:300), but the IRQ is _not_
                 specified, the driver will attempt to autodetect the IRQ.
                 Note that an IRQ is not used for MMPM/2 playback anyway.

        /N:sss   Driver name, an 8-character length string, ending in a $.
                 Do not specify a port number.  Default is "MPU401$".

        /R:yyy   Resolution of MMPM/2 timing.  If the highres timer
                 (TIMER0.SYS) is installed, this parameter tells the MPU-401
                 driver what resolution to use (where yyy is the number of
                 milliseconds) when playing MMPM/2 MIDI streams.  Default is
                 one millisecond.

        /V       Verbose output during boot.  If used, this should be the
                 first parameter.


 6.0 Bugs
 _______

  The Resource Manager is not used, and therefore autodetect could trample
  on other hardware.

  There seems to be a bug in MMPM/2's AUDIO_CAPABILITY code, and therefore
  this driver doesn't use that feature.



 7.0  TRADEMARKS
   __________

  The following terms, denoted by an asterisk (*) in
  this file, are trademarks or registered trademarks of
  IBM Corporation in the United States and/or other
  countries:

    IBM
    OS/2


  IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR
  IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED
  WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND
  MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN
  THIS DOCUMENT.  BY FURNISHING THIS DOCUMENT, IBM
  GRANTS NO LICENSES TO ANY RELATED PATENTS OR
  COPYRIGHTS.

  THIS DRIVER IS COPYRIGHTED BY INTERNATIONAL BUSINESS
  MACHINES CORPORATION.  ALL APPROPRIATE RESTRICTIONS
  APPLY.

                                (End of Document)




ADLIB device driver Version 1.5
technical OS2 support : Christian Gingras

Release of MAY 1996.
